Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1102

reference
758-tree-1
name
1102
tree-preservation-order

undefined

758-tpo-1
uprn
address-text
point
POINT (-1.011913 50.887485)
geometry
MULTIPOLYGON (((-1.011856 50.887479,-1.011859 50.887490,-1.011866 50.887500,-1.011879 50.887508,-1.011895 50.887513,-1.011912 50.887515,-1.011930 50.887513,-1.011946 50.887508,-1.011958 50.887501,-1.011967 50.887491,-1.011970 50.887480,-1.011967 50.887468,-1.011959 50.887458,-1.011947 50.887450,-1.011931 50.887445,-1.011914 50.887443,-1.011896 50.887445,-1.011880 50.887450,-1.011867 50.887458,-1.011859 50.887467,-1.011856 50.887479)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL